The res URI scheme is for files in .sublime-package archives which can be opened via "View Package File" command. I think the only file types where this should be relevant are Python and JSON (maybe XML too). Are you sure that you need that scheme for files with source.bb scope?

The JSON schema contains the definition for a "LSP-html" property in project settings. And the Python code has class definitions with references to things like html/customDataChanged...
Are you sure that is applicable to your language server?

The res URI scheme is for files in .sublime-package archives which can be opened via "View Package File" command. I think the only file types where this should be relevant are Python and JSON (maybe XML too). Are you sure that you need that scheme for files with source.bb scope?

The JSON schema contains the definition for a "LSP-html" property in project settings. And the Python code has class definitions with references to things like html/customDataChanged... Are you sure that is applicable to your language server?

thanks for suggestion, i took the template/example of LSP-html as starting point, i will make some cleanup

The repo was transferred to https://github.com/sublimelsp/LSP-bitbake.

I've also mentioned some of those issues + some more.

Would suggest changing this over-engineered structure to a single plugin.py file like in https://github.com/sublimelsp/LSP-dockerfile/blob/master/plugin.py for example.

And since the server is a published package, remove all files but package.json and package-lock.json from its directory and update renovate.json to not ignore npm updates.

Also update readme to include info about required syntax since without it the server won't start.

Can get inspiration from https://github.com/sublimelsp/LSP-dockerfile/blob/master/README.md maybe

@rchl @jwortmann thanks for suggestion, i have refractor it to use a much simpler architure with sublimelsp/LSP-bitbake#2

should be merge this also? since sublimelsp/LSP-bitbake#2 was merged